 |
List of DNS record types Totally Explained
|
|  |
|
NEW! |
All the latest news in the worlds of
computer gaming,
entertainment,
the environment,
finance,
health,
politics,
science,
stocks & shares,
technology
and much,
much,
more.
|
Everything about List Of Dns Record Types totally explainedThis List of DNS record types provides a convenient index to information about the various kinds of DNS records.
Types of information stored in DNS include the following:
| Code |
Number |
Defining RFC |
Description |
Function |
| A |
1 |
RFC 1035 |
address record |
maps a hostname to a 32-bit IPv4 address. |
| AAAA |
28 |
RFC 3596 |
IPv6 address record |
maps a hostname to a 128-bit IPv6 address. |
| AXFR |
252 |
RFC 1035 |
Full Zone Transfer |
Transfer the entire zone file from the master name server to secondary name servers. |
| CERT |
37 |
RFC 4398 |
Certificate record |
can store PKIX, SPKI, PGP, etc. |
| CNAME |
5 |
RFC 1035 |
canonical name record |
is an alias of one name to another. The A record to which the alias points can be either local or remote - on a foreign name server. This is useful when running multiple services (like an FTP and a webserver) from a single IP address. Each service can then have its own entry in DNS (like ftp.example.com. and www.example.com.). It is also used when running multiple HTTP servers, with different names, on the same physical host. |
| DHCID |
49 |
RFC 4701 |
DHCP identifier |
Used in conjuction with the FQDN option to DHCP |
| DLV |
32769 |
RFC 4431 |
DNSSEC Lookaside Validation record |
for publishing DNSSEC trust anchors outside of the DNS delegation chain. |
| DNAME |
39 |
RFC 2672 |
delegation name |
Unlike the CNAME record which creates a single alias, a DNAME will delegate an entire portion of the DNS tree under a new name. |
| DNSKEY |
48 |
RFC 3755 |
DNS Key record |
The key record used in DNSSEC |
| DS |
43 |
RFC 3658 |
Delegation signer |
The record used to identify the DNSSEC signing key of a delegated zone |
| HIP |
55 |
RFC 5205 |
Host Identity Protocol |
a method of separating the end-point identifier and locator roles of IP addresses. |
IPSECKEY |
45 |
RFC 4025 |
IPSEC Key |
Key record that can be used with IPSEC |
| IXFR |
251 |
RFC 1995 |
Incremental Zone Transfer |
Transfer the changed parts of the zone file from the master name server to secondary name servers. |
KEY |
25 |
RFC 4034 |
Key record |
Used only for TKEY (RFC 2930). Before RFC 3755 was published, this was also used for DNSSEC, but DNSSEC now uses DNSKEY. |
| LOC |
29 |
RFC 1876 |
Location record |
Specifies a geographical location associated with a domain name. |
| MX |
15 |
RFC 1035 |
mail exchange record |
maps a domain name to a list of mail exchange servers for that domain. |
| NAPTR |
35 |
RFC 3403 |
Naming Authority Pointer |
a newer type of DNS record that support regular expression based rewriting. |
| NS |
2 |
RFC 1035 |
name server record |
delegates a DNS zone to be use the given authoritative name servers |
| NSEC |
47 |
RFC 3755 |
Next-Secure record |
Part of DNSSEC. Used to prove that a name doesn't exist. |
| NSEC3PARAM |
51 |
RFC 5155 |
NSEC3 parameters |
Parameter record for use with NSEC3 |
| OPT |
41 |
RFC 2671 |
Option |
This is a "pseudo DNS record type" needed to support EDNS |
| PTR |
12 |
RFC 1035 |
pointer record |
maps an IPv4 address to the canonical name for that host. Setting up a PTR record for a hostname in the in-addr.arpa. domain that corresponds to an IP address implements reverse DNS lookup for that address. For example (at the time of writing), www.icann.net has the IP address 192.0.34.164, but a PTR record maps 164.34.0.192.in-addr.arpa to its canonical name, referrals.icann.org. |
| RRSIG |
46 |
RFC 3755 |
DNSSEC signature |
Signature for a DNSSEC-secured record set |
| SIG |
24 |
RFC 2535 |
Signature |
Signature record used in SIG(0) (RFC 2931). Until RFC 3755 was published, the SIG record was part of DNSSEC; now RRSIG is used for that. |
| SOA |
6 |
RFC 1035 |
start of authority record |
specifies the DNS server providing authoritative information about an Internet domain, the email of the domain administrator, the domain serial number, and several timers relating to refreshing the zone. |
SPF |
99 |
RFC 4408 |
SPF record |
Specified as part of the SPF protocol, as an alternative to storing SPF data in TXT records. |
| SRV |
33 |
RFC 2872 |
Service locator |
a generalized service location record, used for newer protocols instead of creating protocol-specific records such as MX. |
| SSHFP |
44 |
RFC 4255 |
SSH Public Key Fingerprint |
a resource record for publishing SSH public host key fingerprints in the DNS System, in order to aid in verifying the authenticity of the host. |
| TA |
32768 |
None |
DNSSEC Trust Authorities |
Part of a deployment proposal for DNSSEC without a signed DNS root. See the IANA database and Weiler Spec ] for details |
| TKEY |
249 |
RFC 2930 |
Transaction Key |
a record that supports one set of security mechanisms for the DNS. |
| TSIG |
250 |
RFC 2845 |
Transaction Signature |
a record that supports one set of security mechanisms for DNS. |
| TXT |
16 |
RFC 1035 |
Text record |
originally intended to carry arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record is more often used to carry machine-readable data such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework and DomainKeys. |
Other types
Other types of records simply provide information, or experimental data (for example, a WKS record gives a list of servers offering some well known service such as HTTP or POP3 for a domain). Several of these record types are obsolete.
The "type" field is also used in the protocol for various operations; type 255 is a request for "all records of all types", 252 (AXFR) is a request for transfer of a zone, TKEY and TSIG are used for transaction signing (which is different from record signing).
Obsolete record types
Of the records listed at IANA, some are unlikely to be useful, for various reasons. Some are marked obsolete in the list, some are for very obscure services, some are for older versions of services, and some have special notes saying they're "not right".
- Obsolete: MD(3), MF (4), NXT(30), MAILB (253), MAILA (254)
- Mistakes: NB(32), NBSTAT(33) (from RFC 1002); the numbers are now assigned to NIMLOC and SRV.
- Obscure: AFSDB(18), X25(19), ISDN(20), RT(21), NSAP(22), NSAP-PTR(23), PX(26), EID(31), NIMLOC(32), ATMA(34), KX(36), A6(38)
- Experimental: MB(7), MG(8), MR(9), NULL(10)
- Obsoleted by DNSSEC updates (RFC 3755): NXT(30). The domain of applicability for KEY and SIG was also limited to not include DNSSEC use.
- Not in current use: WKS(11), HINFO(13), MINFO(14), RP(17), GPOS(27), SINK(40), APL(42)
- IANA reserved: UINFO(100), UID(101), GID(102), UNSPEC(103)
Further Information
Get more info on 'List Of Dns Record Types'.
|
External Link Exchanges
Do you know how hard it is to get a link from a large encyclopaedia? Well we're different and will prove it. To get a link from us just add the following HTML to your site on a relevant page:
<a href="http://list_of_dns_record_types.totallyexplained.com">List of DNS record types Totally Explained</a>
Then simply click through this link from your web page. Our crawlers will verify your link, extract the title of your web page and instantly add a link back to it. If you like you can remove the words Totally Explained and embed the link in article text.
As long as your link remains in place, we'll keep our link to you right here. Please play fair - our crawlers are watching. Your site must be closely related to this one's topic. Any kind of spamming, dubious practises or removing the link will result in your link from us being dropped and, potentially, your whole site being banned. |
|
|